-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
refactor(routing): Remove backwards compatibility for the routing crate #3015
Conversation
…perswitch into rmove-backwards-compat
…h into rmove-backwards-compat
…h into rmove-backwards-compat
crates/api_models/src/routing.rs
Outdated
pub enum RoutableChoiceKind { | ||
OnlyConnector, | ||
FullStruct, | ||
} | ||
|
||
#[cfg(feature = "connector_choice_bcompat")] | ||
#[derive(Debug, serde::Deserialize, serde::Serialize)] | ||
#[serde(untagged)] | ||
pub enum RoutableChoiceSerde { | ||
OnlyConnector(Box<RoutableConnectors>), | ||
FullStruct { | ||
connector: RoutableConnectors, | ||
#[cfg(feature = "connector_choice_mca_id")] | ||
merchant_connector_id: Option<String>, | ||
#[cfg(not(feature = "connector_choice_mca_id"))] | ||
sub_label: Option<String>, | ||
}, | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We still need support for both types of data (OnlyConnector & FullStruct), as per our current standing. We may take a call to remove support for OnlyConnector
in the future, but that will most probably require DB migrations.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Will remove these fields and open a separate PR
…perswitch into rmove-backwards-compat
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Co-authored-by: Shanks <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
* 'main' of github.com:juspay/hyperswitch: (26 commits) refactor(core): change primary keys in user, user_roles and roles tables (#5374) chore(version): 2024.07.19.1 refactor(connector): make the `original_authorized_amount` optional for MITs with `connector_mandate_details` (#5311) feat(connector): Plaid connector Integration (#3952) feat: encryption service integration to support batch encryption and decryption (#5164) refactor(core): change primary key of refund table (#5367) chore(version): 2024.07.19.0 chore(postman): update Postman collection files Docs: Updating Error codes for documentation purposes (#5314) fix(core): [payouts] failure of payout retrieve when token is expired (#5362) build: remove unused dependencies (#5343) refactor(blocklist): change primary key of blocklist table (#5356) chore: Increasing log coverage for payment method list (#5042) refactor(routing): Remove backwards compatibility for the routing crate (#3015) refactor(merchant_account): change primary key for merchant account (#5327) refactor(router): remove id dependency from merchant connector account, dispute and mandate (#5330) feat(connector): [Itau Bank] Template for payment flows (#5304) chore(version): 2024.07.18.0 refactor(router): Remove the locker call in the psync flow (#5348) feat(router): Add support for passing the domain dynamically in the session call (#5347) ...
Type of Change
Description
Remove the feature flags that were added for providing support for backwards compatibility.
Additional Changes
Motivation and Context
How did you test it?
This PR cannot be tested as it removes the support for backwards compatibility. A sanity for routing must be done.
Checklist
cargo +nightly fmt --all
cargo clippy